home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
opus
/
ohslk20b.zip
/
O-HSLNK.DOC
< prev
Wrap
Text File
|
1992-07-22
|
12KB
|
246 lines
╒╤══╕ ╒══╤╕
╘╛ │ ▄▄▄▄ ▄▄▄▄ ▄ ▄ ▄▄▄▄ ▄ ▄ ▄▄▄▄ ▄ ▄▄▄ ▄▄▄ ▄ ▄ ▄▄ │ ╘╛
│ █ █ █▄▄█ █ █ █▄▄▄ ─── █▄▄█ █▄▄▄ █ █ █ █ █ █▄█▄ │
╘═══█▄▄█ █ █▄▄█ ▄▄▄█ █ █ ▄▄▄█ █▄▄▄ ▄█▄ █ █▄█ █ █════╛
▄▄▄ ▄▄▄ ▄ ▄▄▄▄▄ ▄▄▄▄ ▄▄▄▄ ▄▄▄▄ ▄▄▄▄ ▄▄▄▄ ▄▄▄▄
█ █ █ █ █ █▄ █▄▄█ █▄ █▄▄█ █ █▄
▄█▄ █ █▄█ █ █▄▄▄ █ █▄ █ █ █ █▄▄▄ █▄▄▄
╥ ╥ ╓──╖ ╓──╖
║ ╓╜ ╓──╜ ╫ ╫
╙─╜ o ╙─── o ╙──╜ B
┌────────────────────────────────┐
─────────┤ Written by Dominic Montalto ├─────────
──────┤ For Opus CBCS Versions 1.7x+ ├──────
└────────────────────────────────┘
July 19, 1992
Documentation by Al Filandro
-Opus Hslink Interface 2.0- [2]
-Introduction-
Since Opus is basically a uni-directional bulletin board system, writing
interfaces for bi-directional interfaces can be both time consuming and
frustrating. Most BBS's (Opus included) will only offer an Upload or
Download option to the user at once, thus the user will in Opus' eyes, be
EITHER uploading or downloading. Some very large and complex interfaces
for Opus (Such as Eric Labs "BIOPUS" for Bimodem) solved this problem but
were very tedious to run and even harder to maintain.
O-hslink takes into account the way Opus "views its customers" in that
it will instruct someone using both channels of Ohslink to execute Hslink
again and then allow Opus to ask for a description of the file they just
sent to the bulletin board thus getting credit for the file(s) they've up-
loaded. If the user merely downloads and does not invoke Hslink again, the
program will remain intact until the next time it is used. If the user
downloads more or uploads more files, they will be added to the "extra-file"
listing that O-hslink creates. If the user hangs up for some reason, the
list will remain intact and the next user who uses Hslink will allow the
processing of the list created by prior user. This is essential to allow
the interface to process these files lest Opus will not know what these
files are or where they came from.
-Opus Hslink Interface 2.0- [3]
-Installation-
Prior versions of Opus-Hslink interfaced required a file named "BBS.CTL"
to be in your Opus root directory, version 2.0 of this interface conquers
this problem for those using Hslink on multiline systems or for those
who simply have different names for their Opus control file.
With this version, OHSLINK uses a Dos-environment variable to get its
information of your computers locked DTE rate. This environment will
work with Opdsz/Oshlink and Ymodem G interfaces version 2.0. To set this
environment, place the following line in your autoexec.bat
SET OPUSINT=<Locked DTE Rate>
Where Locked DTE Rate is the what you have your com port locked at
If you are not locking your com port, do NOT use this variable!!
ie:
SET OPUSINT=38400
If this variable is not defined, Opus will revert to the connect
string to get its baud-rate from, and if this differs from your
-Opus Hslink Interface 2.0- [4]
locked DTE rate, Hslink itself will exit with errors.
The Archive enclosed in this package can be renamed to any filename
you desire except "HSLINK.EXE" which is what the interface is looking ou want users to choose "O" to initiate HSLINK. This
for! This is useful if you aleady are using an external protocol with
Opus that begins with the letter 'H'. You can leave it named at "HSLINKS"
as well. You must edit your BBS.CTL (or equivilent) file to add the
interface to Opus' list.
BBS.CTL Example:
%
EXTERNAL Protocol D:\OPUS\DSZ-ZMOD.EXE
EXTERNAL Protocol D:\OPUS\GYMODEMG.EXE
EXTERNAL Protocol D:\OPUS\H-SUPER8.EXE <--Note "H" is already used.
EXTERNAL Protocol D:\OPUS\ASCII.EXE
EXTERNAL Protocol D:\OPUS\IMODEM.EXE
EXTERNAL Protocol D:\OPUS\O-HSLINK.EXE <--- Heres The "O"/Hs-Link
% EXTERNAL Protocol
Refund 140
%
-Opus Hslink Interface 2.0- [5]
Of course, after you are done installing O-HSLINK to your BBS.CTL file,
you will have to SALT (NACL) it so that it is compiled into your BBS.PRM
and recognized by Opus.
-Hslink Advantages-
Hslink (The protocol itself) will provide your BBS with one of the best
protocols ever written for IBM/PC communications. Hs-link allows a user
to send AND receive a file or files simultaneously. This saves both you
and your users time. Unlike "Bi-Modem" or "SuperZmodem" which allow user
chats during this time, Hs/Link offers no such Chat capability (like it was
used often anyways right?), but it does offer a much more stable and secure
protocol that can be accessed through a single Executable file (HSLINK.EXE)
unlike Bimodem or SuperZmodem with their six or seven parts and frustrating
configuration. An asynchronous V32 modem-to-modem connection using Hslink
will provide combined transfer rates of 3300cps and higher with compressed
files!
-Opus Hslink Interface 2.0- [6]
Hslink is the product of Samuel Smith, a fellow BBS operator and programmer.
Although the registered version of HS/Link itself will only provide you with
a status-bar display of the download/upload in progress, I urge you all to
register the protocol as it is well worth it.
==How the Interface Works==
1> Gets the path of the DSZLOG, which is Required.
example SET DSZLOG=<DIRECTORY\DSZ.LOG>
2> The Task is passed from Opus to the interface
3> The old Hslink Log files is deleted.
4> The Control File is read into memory.
5> The Baud maximum is gotten from Dos environment setting
6> Determines to Send or Receive files
7> Check to see if HSLKXTRA.FIL exists Extra Files
not Recognized by Opus (Task Specific ie HSLKEXT01.FIL)
a> If the file exists then each file is copied to
the LOG file
b> Then the interface exits and Opus gets Descriptions
-Opus Hslink Interface 2.0- [7]
for the files
8> If the HSLKXTRA.FIL does not exist then HSLINK.EXE is
searched for in your DOS Path
9> A SENDLIST (Task Specific) is created for multiple files
10> HSLINK is now called and the files are sent or received
11> The DSZLOG is now processed and checked over
a> Any files that were partially received will be
deleted
b> files that all ready exists will be skipped
c> If we were sending to the user all files that were
received will be put into HSLKXTRA.FIL to be
processed later, if files are all ready in
HSLKXTRA.FIL then these will be added to them, and
a message will be sent to the user on how to get
credit for their extra files.
-Opus Hslink Interface 2.0- [8]
-Example Run:-
I Download FILE1.ARJ and Upload FILE2.ARJ and FILE3.ARJ
FILE2.ARJ and FILE3.ARJ are not recognized
This Message gets sent to me......
°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°
▌ If you want to get Credit For your extra files sent, ▌
▌ Just choose UPLOAD with a bogus filename using HSLINK ▌
▌ and the Interface will Trick the BBS into thinking ▌
▌ That you just Uploaded The Files now, then ask you ▌
▌ for Descriptions of them. ▌
▌ NOTICE: Do Not invoke Your HSLINK. ▌
▌ Example:U,choose HSLINK,BOGUS.TXT ▌
°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°
Make the above CLEAR to your users
-Opus Hslink Interface 2.0- [9]
[example continued]
File area 02 .. NewUploads New Uploads on Cygnus X-I
------------------------------------------------------------
FILES: U;H anyname.ext <ENTER>
The Interface now runs and finds the HSLKXTRA.FIL list
and copies them to the log and exits, then Opus finds these files
in the LOG file and Asks for descriptions.
[Opus:]
Describe FILE2.ARJ : ______________________________________________
Describe FILE2.ARJ : ______________________________________________
Transfer Successful....... Etc..Etc..
-Opus Hslink Interface 2.0- [10]
Credits and Revisions:
----------------------
Opus is a Copyright (C)1986-1992 of Wynn Wagner III.
Hs/Link is a Copyright (C)1991-1992 of Samuel H. Smith (Tool Shop BBS).
Bimodem is a Copyright (C)1990-1992 of Erik Labs.
[Rev .5] 01/3/92 Wrote and Tested O-HSLINK
[Rev .6] 01/5/92 Fixed Upload Description Problem
[Rv 1.0] 1/12/92 More code, alternate program added;First General Release
[Rv 1.1] 1/23/92 Wide-Beta Test...Changed minor coding/paths corrected
[Rv 1.2] 2/26/92 Hslink 1.01 Con/Aux bugfix in Protocol <Not Released>
[Rv 1.3] 3/03/92 Changed Upload instructions. Made Sendlist and Extrafile
listings TASK-Specific for better tweaking abilities to
those brave souls running multi-line Opus's.
[Rv 2.0] 7/14/92 Added environment variable..added 8088 instruction mix
(should work on XT's now!) changed several bugs in path
[Rv 2.0a]7/15/92 Fixed Documentation...Env Var is 'OPUSINT' NOT 'OpusLink'
[Rv 2.0b]7/19/92 Files > 1Megs should process without error now.
-Opus Hslink Interface 2.0- [11]
If you are using Opus-Hslink, please consider sending a small
donation of $5 to keep the upgrades coming. If you have any
extra floppies that would be fine too <Grin>.
Dom Montalto
1617 Huckins Road
Cheshire, Ct USA 06410
Opus-link has been tested with Opus versions 1.70, 1.72, 1.73
and Opus 1.99, however there is no guarantee that it will work
on Opus 2.0 when it is released as that version is still in
Gamma stage as of this writing. If you have problems, questions
or suggestions for future versions of O-Hslink, send Netmail to
Cygnus X-I (1:141/885, 8:909/10, 23:703/8, 65:150/885) or address
question to Al Filandro in the Opus-Sysops MEADOW conference.
Thank you for your support!